@bilaljavaid01 Localhost is a special case. Your Omega2 has a localhost, every one of your Omega2 has a local host. Each of these localhost points to themselves, so if from my machine I try to ping localhost, it will ping my machine, not your Omega2. If you want any machine to be able to connect to your Omega2, you need to have your flask app listen on the externally accessible IP address, otherwise, no other machine will be able to access it. Use the command ifconfig to find the externally accessible address you can see here, my IP for the apcli0 interface is 192.168.1.219: apcli0 Link encap:Ethernet HWaddr 40:A3:6B:C3:22:61 inet addr:192.168.1.219 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::42a3:6bff:fec3:2261/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:1629 overruns:0 frame:0 So I would configure my server to listen on that address so other machines can connect to it. Your IP will be something different.

@Nagarjuna-Reddy It is very difficult to help you if you do not provide technical information about your circuit. Are you using a USB to TTL converter? What happened to ttyUSB0 and ttyUSB1? Have you looked at the system log to see if something is wrong?

@crispyoz Yep....I knew that! ;^)

@Nagarjuna-Reddy use logread command then use grep to filter.

Hi crispyoz, one of onion omega developer(Lazar Demin) said below reasons Hi Nagarjuna, Since SPI flash cannot be easily connected and disconnected like USB storage or SD cards, the Linux kernel does not support automatic detection of SPI flash devices or partitions on the devices. Instead, the SPI flash must be defined in the Kernel Device Tree. See how the Omega's internal flash device and partitions are defined in the device tree specification (DTS) here: https://github.com/OnionIoT/source/blob/openwrt-18.06/target/linux/ramips/dts/OMEGA2.dtsi#L103 To support an external flash, you'll need to: Add the SPI flash & it's partitions to the DTS build a new firmware with the modified DTS. I have verified it clearly. but I am worrying about onion guys are saying(Onion Corporation is not responsible for any damage to your device caused by using custom firmware or packages not built and released by Onion Corporation). can you please help me sir how to add SPI code in custom firmware for detection of external SPI bus device.

@William-Scott Hi Bill, I am interested in retaining your services for a 'little' wet err web work. txt 4415050723 please.

@Ammar-Assad using shell edit: I forgot to mention Baud rate, you should use 115200 while read -r line < /dev/ttyS1; do echo $line # do whatever you want with $line done using "C" termios libriary tldp Serial-Programming-HOWTO

In this days I tried cross-compile both with VM Ubuntu and with Docker Toolbox but I wasn't able to include bluetooth library. Does anyone know how to do it? For the test, I used this example: http://people.csail.mit.edu/albert/bluez-intro/c404.html Edit: I found in Docker the bluez-lib and they run well but work in that conteiner is laborious (I have to use transfer.sh website to transfer files). Where can I found the Makefile to compile bluez-lib in the LEDE Configurator in order to use it in Ubuntu too?

@Aman-Chawla Looks like you nailed it! Now figure out why the file system is filled up and you'll be good to go. --Bill